Method and apparatus for video coding

ABSTRACT

Aspects of the disclosure provide methods and apparatuses for video encoding/decoding. An apparatus for video decoding includes processing circuitry. The processing circuitry checks an inferable condition for a flag of a specific prediction mode for a current block before parsing the flag of the specific prediction mode for the current block from a coded video bitstream. The specific prediction mode is one of a plurality of inter picture prediction modes. When the inferable condition indicates that the flag is inferable, the processing circuitry infers the flag without parsing the flag from the coded video bitstream. When the inferable condition indicates uncertainty for inferring the flag, the processing circuitry parses the flag from the coded video bitstream. Then, the processing circuitry reconstructs the current block according to the specific prediction mode when the flag is indicative of an application of the specific prediction mode on the current block.

INCORPORATION BY REFERENCE

This present application is a continuation of and claims priority to U.S. patent application Ser. No. 16/865,052, filed May 1, 2020, which claims the benefit of priority to U.S. Provisional Application No. 62/849,105, “MERGE MODE SIGNALING” filed on May 16, 2019. The benefit of priority is claimed to each of the foregoing, and the entire contents of each of the foregoing are incorporated herein by reference.

TECHNICAL FIELD

The present disclosure describes embodiments generally related to video coding.

BACKGROUND

The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

Video coding and decoding can be performed using inter-picture prediction with motion compensation. Uncompressed digital video can include a series of pictures, each picture having a spatial dimension of, for example, 1920×1080 luminance samples and associated chrominance samples. The series of pictures can have a fixed or variable picture rate (informally also known as frame rate), of, for example 60 pictures per second or 60 Hz. Uncompressed video has significant bitrate requirements. For example, 1080p604:2:0 video at 8 bit per sample (1920x1080 luminance sample resolution at 60 Hz frame rate) requires close to 1.5 Gbit/s bandwidth. An hour of such video requires more than 600 GBytes of storage space.

One purpose of video coding and decoding can be the reduction of redundancy in the input video signal, through compression. Compression can help reduce the aforementioned bandwidth or storage space requirements, in some cases by two orders of magnitude or more. Both lossless and lossy compression, as well as a combination thereof can be employed. Lossless compression refers to techniques where an exact copy of the original signal can be reconstructed from the compressed original signal. When using lossy compression, the reconstructed signal may not be identical to the original signal, but the distortion between original and reconstructed signals is small enough to make the reconstructed signal useful for the intended application. In the case of video, lossy compression is widely employed. The amount of distortion tolerated depends on the application; for example, users of certain consumer streaming applications may tolerate higher distortion than users of television distribution applications. The compression ratio achievable can reflect that: higher allowable/tolerable distortion can yield higher compression ratios.

Motion compensation can be a lossy compression technique and can relate to techniques where a block of sample data from a previously reconstructed picture or part thereof (reference picture), after being spatially shifted in a direction indicated by a motion vector (MV henceforth), is used for the prediction of a newly reconstructed picture or picture part. In some cases, the reference picture can be the same as the picture currently under reconstruction. MVs can have two dimensions X and Y, or three dimensions, the third being an indication of the reference picture in use (the latter, indirectly, can be a time dimension).

In some video compression techniques, an MV applicable to a certain area of sample data can be predicted from other MVs, for example from those related to another area of sample data spatially adjacent to the area under reconstruction, and preceding that MV in decoding order. Doing so can substantially reduce the amount of data required for coding the MV, thereby removing redundancy and increasing compression. MV prediction can work effectively, for example, because when coding an input video signal derived from a camera (known as natural video) there is a statistical likelihood that areas larger than the area to which a single MV is applicable move in a similar direction and, therefore, can in some cases be predicted using a similar motion vector derived from MVs of neighboring area. That results in the MV found for a given area to be similar or the same as the MV predicted from the surrounding MVs, and that in turn can be represented, after entropy coding, in a smaller number of bits than what would be used if coding the MV directly. In some cases, MV prediction can be an example of lossless compression of a signal (namely: the MVs) derived from the original signal (namely: the sample stream). In other cases, MV prediction itself can be lossy, for example because of rounding errors when calculating a predictor from several surrounding MVs.

Various MV prediction mechanisms are described in H.265/HEVC (ITU-T Rec. H.265, “High Efficiency Video Coding”, December 2016). Out of the many MV prediction mechanisms that H.265 offers, described here is a technique henceforth referred to as “spatial merge”.

Referring to FIG. 1, a current block (101) comprises samples that have been found by the encoder during the motion search process to be predictable from a previous block of the same size that has been spatially shifted. Instead of coding that MV directly, the MV can be derived from metadata associated with one or more reference pictures, for example from the most recent (in decoding order) reference picture, using the MV associated with either one of five surrounding samples, denoted A0, A1, and B0, B1, B2 (102 through 106, respectively). In H.265, the MV prediction can use predictors from the same reference picture that the neighboring block is using.

SUMMARY

Aspects of the disclosure provide methods and apparatuses for video encoding/decoding. In some examples, an apparatus for video decoding includes receiving circuitry and processing circuitry. The processing circuitry checks an inferable condition for a flag of a specific prediction mode for a current block before parsing the flag of the specific prediction mode for the current block from a coded video bitstream. The specific prediction mode is one of a plurality of inter picture prediction modes. When the inferable condition indicates that the flag is inferable, the processing circuitry infers the flag without parsing the flag from the coded video bitstream. When the inferable condition indicates uncertainty for inferring the flag, the processing circuitry parses the flag from the coded video bitstream. Then, the processing circuitry reconstructs the current block according to the specific prediction mode when the flag is indicative of an application of the specific prediction mode on the current block.

In some embodiments, the processing circuitry checks the inferable condition for the flag based on allowability of one or more other modes in the plurality of inter picture prediction modes. In an embodiment, the allowability of another mode is determined based on size information of the current block.

In some embodiments, the flag is one of a regular flag of a regular merge/skip mode, a merge with motion vector difference (MMVD) flag of a MMVD mode, a sub-block flag of a sub-block based merge/skip mode, a combined intra inter prediction (CIIP) flag of a CIIP mode, a triangle flag of a triangle partition mode.

In an embodiment, the specific prediction mode is ahead of the one or more modes in a tree structure for a prediction mode decision.

In some examples, the inferable condition is a combination of allowability of the specific prediction mode and allowability of other modes that are behind the specific prediction modes in a tree structure for a prediction mode decision. In an example, the inferable condition indicates that the flag is inferable when the allowability of the specific prediction mode indicates that the specific prediction mode is not allowed. In another example, the inferable condition indicates that the flag is inferable when the allowability of the other modes indicates that none of the other modes is allowed.

In some embodiments, the allowability of another mode is determined based on at least one of a sequence parameter set (SPS), a picture parameter set (PPS), a slice header, tile information, and tile group information.

Aspects of the disclosure also provide a non-transitory computer-readable medium storing instructions which when executed by a computer for video decoding cause the computer to perform the method for video decoding.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features, the nature, and various advantages of the disclosed subject matter will be more apparent from the following detailed description and the accompanying drawings in which:

FIG. 1 is a schematic illustration of a current block and its surrounding spatial merge candidates in one example.

FIG. 2 is a schematic illustration of a simplified block diagram of a communication system (200) in accordance with an embodiment.

FIG. 3 is a schematic illustration of a simplified block diagram of a communication system (300) in accordance with an embodiment.

FIG. 4 is a schematic illustration of a simplified block diagram of a decoder in accordance with an embodiment.

FIG. 5 is a schematic illustration of a simplified block diagram of an encoder in accordance with an embodiment.

FIG. 6 shows a block diagram of an encoder in accordance with another embodiment.

FIG. 7 shows a block diagram of a decoder in accordance with another embodiment.

FIG. 8 shows a flow chart of an algorithm for an encoder (or decoder) to signal (parse) merge mode flags.

FIG. 9 shows flow chart outlining a process example according to some embodiments of the disclosure.

FIG. 10 is a schematic illustration of a computer system in accordance with an embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

FIG. 2 illustrates a simplified block diagram of a communication system (200) according to an embodiment of the present disclosure. The communication system (200) includes a plurality of terminal devices that can communicate with each other, via, for example, a network (250). For example, the communication system (200) includes a first pair of terminal devices (210) and (220) interconnected via the network (250). In the FIG. 2 example, the first pair of terminal devices (210) and (220) performs unidirectional transmission of data. For example, the terminal device (210) may code video data (e.g., a stream of video pictures that are captured by the terminal device (210)) for transmission to the other terminal device (220) via the network (250). The encoded video data can be transmitted in the form of one or more coded video bitstreams. The terminal device (220) may receive the coded video data from the network (250), decode the coded video data to recover the video pictures and display video pictures according to the recovered video data. Unidirectional data transmission may be common in media serving applications and the like.

In another example, the communication system (200) includes a second pair of terminal devices (230) and (240) that performs bidirectional transmission of coded video data that may occur, for example, during videoconferencing. For bidirectional transmission of data, in an example, each terminal device of the terminal devices (230) and (240) may code video data (e.g., a stream of video pictures that are captured by the terminal device) for transmission to the other terminal device of the terminal devices (230) and (240) via the network (250). Each terminal device of the terminal devices (230) and (240) also may receive the coded video data transmitted by the other terminal device of the terminal devices (230) and (240), and may decode the coded video data to recover the video pictures and may display video pictures at an accessible display device according to the recovered video data.

In the FIG. 2 example, the terminal devices (210), (220), (230) and (240) may be illustrated as servers, personal computers and smart phones but the principles of the present disclosure may be not so limited. Embodiments of the present disclosure find application with laptop computers, tablet computers, media players and/or dedicated video conferencing equipment. The network (250) represents any number of networks that convey coded video data among the terminal devices (210), (220), (230) and (240), including for example wireline (wired) and/or wireless communication networks. The communication network (250) may exchange data in circuit-switched and/or packet-switched channels. Representative networks include telecommunications networks, local area networks, wide area networks and/or the Internet. For the purposes of the present discussion, the architecture and topology of the network (250) may be immaterial to the operation of the present disclosure unless explained herein below.

FIG. 3 illustrates, as an example for an application for the disclosed subject matter, the placement of a video encoder and a video decoder in a streaming environment. The disclosed subject matter can be equally applicable to other video enabled applications, including, for example, video conferencing, digital TV, storing of compressed video on digital media including CD, DVD, memory stick and the like, and so on.

A streaming system may include a capture subsystem (313), that can include a video source (301), for example a digital camera, creating for example a stream of video pictures (302) that are uncompressed. In an example, the stream of video pictures (302) includes samples that are taken by the digital camera. The stream of video pictures (302), depicted as a bold line to emphasize a high data volume when compared to encoded video data (304) (or coded video bitstreams), can be processed by an electronic device (320) that includes a video encoder (303) coupled to the video source (301). The video encoder (303) can include hardware, software, or a combination thereof to enable or implement aspects of the disclosed subject matter as described in more detail below. The encoded video data (304) (or encoded video bitstream (304)), depicted as a thin line to emphasize the lower data volume when compared to the stream of video pictures (302), can be stored on a streaming server (305) for future use. One or more streaming client subsystems, such as client subsystems (306) and (308) in FIG. 3 can access the streaming server (305) to retrieve copies (307) and (309) of the encoded video data (304). A client subsystem (306) can include a video decoder (310), for example, in an electronic device (330). The video decoder (310) decodes the incoming copy (307) of the encoded video data and creates an outgoing stream of video pictures (311) that can be rendered on a display (312) (e.g., display screen) or other rendering device (not depicted). In some streaming systems, the encoded video data (304), (307), and (309) (e.g., video bitstreams) can be encoded according to certain video coding/compression standards. Examples of those standards include ITU-T Recommendation H.265. In an example, a video coding standard under development is informally known as Versatile Video Coding (VVC). The disclosed subject matter may be used in the context of VVC.

It is noted that the electronic devices (320) and (330) can include other components (not shown). For example, the electronic device (320) can include a video decoder (not shown) and the electronic device (330) can include a video encoder (not shown) as well.

FIG. 4 shows a block diagram of a video decoder (410) according to an embodiment of the present disclosure. The video decoder (410) can be included in an electronic device (430). The electronic device (430) can include a receiver (431) (e.g., receiving circuitry). The video decoder (410) can be used in the place of the video decoder (310) in the FIG. 3 example.

The receiver (431) may receive one or more coded video sequences to be decoded by the video decoder (410); in the same or another embodiment, one coded video sequence at a time, where the decoding of each coded video sequence is independent from other coded video sequences. The coded video sequence may be received from a channel (401), which may be a hardware/software link to a storage device which stores the encoded video data. The receiver (431) may receive the encoded video data with other data, for example, coded audio data and/or ancillary data streams, that may be forwarded to their respective using entities (not depicted). The receiver (431) may separate the coded video sequence from the other data. To combat network jitter, a buffer memory (415) may be coupled in between the receiver (431) and an entropy decoder/parser (420) (“parser (420)” henceforth). In certain applications, the buffer memory (415) is part of the video decoder (410). In others, it can be outside of the video decoder (410) (not depicted). In still others, there can be a buffer memory (not depicted) outside of the video decoder (410), for example to combat network jitter, and in addition another buffer memory (415) inside the video decoder (410), for example to handle playout timing. When the receiver (431) is receiving data from a store/forward device of sufficient bandwidth and controllability, or from an isosynchronous network, the buffer memory (415) may not be needed, or can be small. For use on best effort packet networks such as the Internet, the buffer memory (415) may be required, can be comparatively large and can be advantageously of adaptive size, and may at least partially be implemented in an operating system or similar elements (not depicted) outside of the video decoder (410).

The video decoder (410) may include the parser (420) to reconstruct symbols (421) from the coded video sequence. Categories of those symbols include information used to manage operation of the video decoder (410), and potentially information to control a rendering device such as a render device (412) (e.g., a display screen) that is not an integral part of the electronic device (430) but can be coupled to the electronic device (430), as was shown in FIG. 4. The control information for the rendering device(s) may be in the form of Supplemental Enhancement Information (SEI messages) or Video Usability Information (VUI) parameter set fragments (not depicted). The parser (420) may parse/entropy-decode the coded video sequence that is received. The coding of the coded video sequence can be in accordance with a video coding technology or standard, and can follow various principles, including variable length coding, Huffman coding, arithmetic coding with or without context sensitivity, and so forth. The parser (420) may extract from the coded video sequence, a set of subgroup parameters for at least one of the subgroups of pixels in the video decoder, based upon at least one parameter corresponding to the group. Subgroups can include Groups of Pictures (GOPs), pictures, tiles, slices, macroblocks, Coding Units (CUs), blocks, Transform Units (TUs), Prediction Units (PUs) and so forth. The parser (420) may also extract from the coded video sequence information such as transform coefficients, quantizer parameter values, motion vectors, and so forth.

The parser (420) may perform an entropy decoding/parsing operation on the video sequence received from the buffer memory (415), so as to create symbols (421).

Reconstruction of the symbols (421) can involve multiple different units depending on the type of the coded video picture or parts thereof (such as: inter and intra picture, inter and intra block), and other factors. Which units are involved, and how, can be controlled by the subgroup control information that was parsed from the coded video sequence by the parser (420). The flow of such subgroup control information between the parser (420) and the multiple units below is not depicted for clarity.

Beyond the functional blocks already mentioned, the video decoder (410) can be conceptually subdivided into a number of functional units as described below. In a practical implementation operating under commercial constraints, many of these units interact closely with each other and can, at least partly, be integrated into each other. However, for the purpose of describing the disclosed subject matter, the conceptual subdivision into the functional units below is appropriate.

A first unit is the scaler/inverse transform unit (451). The scaler/inverse transform unit (451) receives a quantized transform coefficient as well as control information, including which transform to use, block size, quantization factor, quantization scaling matrices, etc. as symbol(s) (421) from the parser (420). The scaler/inverse transform unit (451) can output blocks comprising sample values, that can be input into aggregator (455).

In some cases, the output samples of the scaler/inverse transform (451) can pertain to an intra coded block; that is: a block that is not using predictive information from previously reconstructed pictures, but can use predictive information from previously reconstructed parts of the current picture. Such predictive information can be provided by an intra picture prediction unit (452). In some cases, the intra picture prediction unit (452) generates a block of the same size and shape of the block under reconstruction, using surrounding already reconstructed information fetched from the current picture buffer (458). The current picture buffer (458) buffers, for example, partly reconstructed current picture and/or fully reconstructed current picture. The aggregator (455), in some cases, adds, on a per sample basis, the prediction information the intra prediction unit (452) has generated to the output sample information as provided by the scaler/inverse transform unit (451).

In other cases, the output samples of the scaler/inverse transform unit (451) can pertain to an inter coded, and potentially motion compensated block. In such a case, a motion compensation prediction unit (453) can access reference picture memory (457) to fetch samples used for prediction. After motion compensating the fetched samples in accordance with the symbols (421) pertaining to the block, these samples can be added by the aggregator (455) to the output of the scaler/inverse transform unit (451) (in this case called the residual samples or residual signal) so as to generate output sample information. The addresses within the reference picture memory (457) from where the motion compensation prediction unit (453) fetches prediction samples can be controlled by motion vectors, available to the motion compensation prediction unit (453) in the form of symbols (421) that can have, for example X, Y, and reference picture components. Motion compensation also can include interpolation of sample values as fetched from the reference picture memory (457) when sub-sample exact motion vectors are in use, motion vector prediction mechanisms, and so forth.

The output samples of the aggregator (455) can be subject to various loop filtering techniques in the loop filter unit (456). Video compression technologies can include in-loop filter technologies that are controlled by parameters included in the coded video sequence (also referred to as coded video bitstream) and made available to the loop filter unit (456) as symbols (421) from the parser (420), but can also be responsive to meta-information obtained during the decoding of previous (in decoding order) parts of the coded picture or coded video sequence, as well as responsive to previously reconstructed and loop-filtered sample values.

The output of the loop filter unit (456) can be a sample stream that can be output to the render device (412) as well as stored in the reference picture memory (457) for use in future inter-picture prediction.

Certain coded pictures, once fully reconstructed, can be used as reference pictures for future prediction. For example, once a coded picture corresponding to a current picture is fully reconstructed and the coded picture has been identified as a reference picture (by, for example, the parser (420)), the current picture buffer (458) can become a part of the reference picture memory (457), and a fresh current picture buffer can be reallocated before commencing the reconstruction of the following coded picture.

The video decoder (410) may perform decoding operations according to a predetermined video compression technology in a standard, such as ITU-T Rec. H.265. The coded video sequence may conform to a syntax specified by the video compression technology or standard being used, in the sense that the coded video sequence adheres to both the syntax of the video compression technology or standard and the profiles as documented in the video compression technology or standard. Specifically, a profile can select certain tools as the only tools available for use under that profile from all the tools available in the video compression technology or standard. Also necessary for compliance can be that the complexity of the coded video sequence is within bounds as defined by the level of the video compression technology or standard. In some cases, levels restrict the maximum picture size, maximum frame rate, maximum reconstruction sample rate (measured in, for example megasamples per second), maximum reference picture size, and so on. Limits set by levels can, in some cases, be further restricted through Hypothetical Reference Decoder (HRD) specifications and metadata for HRD buffer management signaled in the coded video sequence.

In an embodiment, the receiver (431) may receive additional (redundant) data with the encoded video. The additional data may be included as part of the coded video sequence(s). The additional data may be used by the video decoder (410) to properly decode the data and/or to more accurately reconstruct the original video data. Additional data can be in the form of, for example, temporal, spatial, or signal noise ratio (SNR) enhancement layers, redundant slices, redundant pictures, forward error correction codes, and so on.

FIG. 5 shows a block diagram of a video encoder (503) according to an embodiment of the present disclosure. The video encoder (503) is included in an electronic device (520). The electronic device (520) includes a transmitter (540) (e.g., transmitting circuitry). The video encoder (503) can be used in the place of the video encoder (303) in the FIG. 3 example.

The video encoder (503) may receive video samples from a video source (501) (that is not part of the electronic device (520) in the FIG. 5 example) that may capture video image(s) to be coded by the video encoder (503). In another example, the video source (501) is a part of the electronic device (520).

The video source (501) may provide the source video sequence to be coded by the video encoder (503) in the form of a digital video sample stream that can be of any suitable bit depth (for example: 8 bit, 10 bit, 12 bit, . . . ), any colorspace (for example, BT.601 Y CrCB, RGB, . . . ), and any suitable sampling structure (for example Y CrCb 4:2:0, Y CrCb 4:4:4). In a media serving system, the video source (501) may be a storage device storing previously prepared video. In a videoconferencing system, the video source (501) may be a camera that captures local image information as a video sequence. Video data may be provided as a plurality of individual pictures that impart motion when viewed in sequence. The pictures themselves may be organized as a spatial array of pixels, wherein each pixel can comprise one or more samples depending on the sampling structure, color space, etc. in use. A person skilled in the art can readily understand the relationship between pixels and samples. The description below focuses on samples.

According to an embodiment, the video encoder (503) may code and compress the pictures of the source video sequence into a coded video sequence (543) in real time or under any other time constraints as required by the application. Enforcing appropriate coding speed is one function of a controller (550). In some embodiments, the controller (550) controls other functional units as described below and is functionally coupled to the other functional units. The coupling is not depicted for clarity. Parameters set by the controller (550) can include rate control related parameters (picture skip, quantizer, lambda value of rate-distortion optimization techniques, . . . ), picture size, group of pictures (GOP) layout, maximum motion vector search range, and so forth. The controller (550) can be configured to have other suitable functions that pertain to the video encoder (503) optimized for a certain system design.

In some embodiments, the video encoder (503) is configured to operate in a coding loop. As an oversimplified description, in an example, the coding loop can include a source coder (530) (e.g., responsible for creating symbols, such as a symbol stream, based on an input picture to be coded, and a reference picture(s)), and a (local) decoder (533) embedded in the video encoder (503). The decoder (533) reconstructs the symbols to create the sample data in a similar manner as a (remote) decoder also would create (as any compression between symbols and coded video bitstream is lossless in the video compression technologies considered in the disclosed subject matter). The reconstructed sample stream (sample data) is input to the reference picture memory (534). As the decoding of a symbol stream leads to bit-exact results independent of decoder location (local or remote), the content in the reference picture memory (534) is also bit exact between the local encoder and remote encoder. In other words, the prediction part of an encoder “sees” as reference picture samples exactly the same sample values as a decoder would “see” when using prediction during decoding. This fundamental principle of reference picture synchronicity (and resulting drift, if synchronicity cannot be maintained, for example because of channel errors) is used in some related arts as well.

The operation of the “local” decoder (533) can be the same as of a “remote” decoder, such as the video decoder (410), which has already been described in detail above in conjunction with FIG. 4. Briefly referring also to FIG. 4, however, as symbols are available and encoding/decoding of symbols to a coded video sequence by an entropy coder (545) and the parser (420) can be lossless, the entropy decoding parts of the video decoder (410), including the buffer memory (415), and parser (420) may not be fully implemented in the local decoder (533).

An observation that can be made at this point is that any decoder technology except the parsing/entropy decoding that is present in a decoder also necessarily needs to be present, in substantially identical functional form, in a corresponding encoder. For this reason, the disclosed subject matter focuses on decoder operation. The description of encoder technologies can be abbreviated as they are the inverse of the comprehensively described decoder technologies. Only in certain areas a more detail description is required and provided below.

During operation, in some examples, the source coder (530) may perform motion compensated predictive coding, which codes an input picture predictively with reference to one or more previously-coded picture from the video sequence that were designated as “reference pictures”. In this manner, the coding engine (532) codes differences between pixel blocks of an input picture and pixel blocks of reference picture(s) that may be selected as prediction reference(s) to the input picture.

The local video decoder (533) may decode coded video data of pictures that may be designated as reference pictures, based on symbols created by the source coder (530). Operations of the coding engine (532) may advantageously be lossy processes. When the coded video data may be decoded at a video decoder (not shown in FIG. 5), the reconstructed video sequence typically may be a replica of the source video sequence with some errors. The local video decoder (533) replicates decoding processes that may be performed by the video decoder on reference pictures and may cause reconstructed reference pictures to be stored in the reference picture cache (534). In this manner, the video encoder (503) may store copies of reconstructed reference pictures locally that have common content as the reconstructed reference pictures that will be obtained by a far-end video decoder (absent transmission errors).

The predictor (535) may perform prediction searches for the coding engine (532). That is, for a new picture to be coded, the predictor (535) may search the reference picture memory (534) for sample data (as candidate reference pixel blocks) or certain metadata such as reference picture motion vectors, block shapes, and so on, that may serve as an appropriate prediction reference for the new pictures. The predictor (535) may operate on a sample block-by-pixel block basis to find appropriate prediction references. In some cases, as determined by search results obtained by the predictor (535), an input picture may have prediction references drawn from multiple reference pictures stored in the reference picture memory (534).

The controller (550) may manage coding operations of the source coder (530), including, for example, setting of parameters and subgroup parameters used for encoding the video data.

Output of all aforementioned functional units may be subjected to entropy coding in the entropy coder (545). The entropy coder (545) translates the symbols as generated by the various functional units into a coded video sequence, by lossless compressing the symbols according to technologies such as Huffman coding, variable length coding, arithmetic coding, and so forth.

The transmitter (540) may buffer the coded video sequence(s) as created by the entropy coder (545) to prepare for transmission via a communication channel (560), which may be a hardware/software link to a storage device which would store the encoded video data. The transmitter (540) may merge coded video data from the video coder (503) with other data to be transmitted, for example, coded audio data and/or ancillary data streams (sources not shown).

The controller (550) may manage operation of the video encoder (503). During coding, the controller (550) may assign to each coded picture a certain coded picture type, which may affect the coding techniques that may be applied to the respective picture. For example, pictures often may be assigned as one of the following picture types:

An Intra Picture (I picture) may be one that may be coded and decoded without using any other picture in the sequence as a source of prediction. Some video codecs allow for different types of intra pictures, including, for example Independent Decoder Refresh (“IDR”) Pictures. A person skilled in the art is aware of those variants of I pictures and their respective applications and features.

A predictive picture (P picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most one motion vector and reference index to predict the sample values of each block.

A bi-directionally predictive picture (B Picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most two motion vectors and reference indices to predict the sample values of each block. Similarly, multiple-predictive pictures can use more than two reference pictures and associated metadata for the reconstruction of a single block.

Source pictures commonly may be subdivided spatially into a plurality of sample blocks (for example, blocks of 4×4, 8×8, 4×8, or 16×16 samples each) and coded on a block-by-block basis. Blocks may be coded predictively with reference to other (already coded) blocks as determined by the coding assignment applied to the blocks' respective pictures. For example, blocks of I pictures may be coded non-predictively or they may be coded predictively with reference to already coded blocks of the same picture (spatial prediction or intra prediction). Pixel blocks of P pictures may be coded predictively, via spatial prediction or via temporal prediction with reference to one previously coded reference picture. Blocks of B pictures may be coded predictively, via spatial prediction or via temporal prediction with reference to one or two previously coded reference pictures.

The video encoder (503) may perform coding operations according to a predetermined video coding technology or standard, such as ITU-T Rec. H.265. In its operation, the video encoder (503) may perform various compression operations, including predictive coding operations that exploit temporal and spatial redundancies in the input video sequence. The coded video data, therefore, may conform to a syntax specified by the video coding technology or standard being used.

In an embodiment, the transmitter (540) may transmit additional data with the encoded video. The source coder (530) may include such data as part of the coded video sequence. Additional data may comprise temporal/spatial/SNR enhancement layers, other forms of redundant data such as redundant pictures and slices, SEI messages, VUI parameter set fragments, and so on.

A video may be captured as a plurality of source pictures (video pictures) in a temporal sequence. Intra-picture prediction (often abbreviated to intra prediction) makes use of spatial correlation in a given picture, and inter-picture prediction makes uses of the (temporal or other) correlation between the pictures. In an example, a specific picture under encoding/decoding, which is referred to as a current picture, is partitioned into blocks. When a block in the current picture is similar to a reference block in a previously coded and still buffered reference picture in the video, the block in the current picture can be coded by a vector that is referred to as a motion vector. The motion vector points to the reference block in the reference picture, and can have a third dimension identifying the reference picture, in case multiple reference pictures are in use.

In some embodiments, a bi-prediction technique can be used in the inter-picture prediction. According to the bi-prediction technique, two reference pictures, such as a first reference picture and a second reference picture that are both prior in decoding order to the current picture in the video (but may be in the past and future, respectively, in display order) are used. A block in the current picture can be coded by a first motion vector that points to a first reference block in the first reference picture, and a second motion vector that points to a second reference block in the second reference picture. The block can be predicted by a combination of the first reference block and the second reference block.

Further, a merge mode technique can be used in the inter-picture prediction to improve coding efficiency.

According to some embodiments of the disclosure, predictions, such as inter-picture predictions and intra-picture predictions are performed in the unit of blocks. For example, according to the HEVC standard, a picture in a sequence of video pictures is partitioned into coding tree units (CTU) for compression, the CTUs in a picture have the same size, such as 64×64 pixels, 32×32 pixels, or 16×16 pixels. In general, a CTU includes three coding tree blocks (CTBs), which are one luma CTB and two chroma CTBs. Each CTU can be recursively quadtree split into one or multiple coding units (CUs). For example, a CTU of 64×64 pixels can be split into one CU of 64×64 pixels, or 4 CUs of 32×32 pixels, or 16 CUs of 16×16 pixels. In an example, each CU is analyzed to determine a prediction type for the CU, such as an inter prediction type or an intra prediction type. The CU is split into one or more prediction units (PUs) depending on the temporal and/or spatial predictability. Generally, each PU includes a luma prediction block (PB), and two chroma PBs. In an embodiment, a prediction operation in coding (encoding/decoding) is performed in the unit of a prediction block. Using a luma prediction block as an example of a prediction block, the prediction block includes a matrix of values (e.g., luma values) for pixels, such as 8×8 pixels, 16×16 pixels, 8×16 pixels, 16×8 pixels, and the like.

FIG. 6 shows a diagram of a video encoder (603) according to another embodiment of the disclosure. The video encoder (603) is configured to receive a processing block (e.g., a prediction block) of sample values within a current video picture in a sequence of video pictures, and encode the processing block into a coded picture that is part of a coded video sequence. In an example, the video encoder (603) is used in the place of the video encoder (303) in the FIG. 3 example.

In an HEVC example, the video encoder (603) receives a matrix of sample values for a processing block, such as a prediction block of 8×8 samples, and the like. The video encoder (603) determines whether the processing block is best coded using intra mode, inter mode, or bi-prediction mode using, for example, rate-distortion optimization. When the processing block is to be coded in intra mode, the video encoder (603) may use an intra prediction technique to encode the processing block into the coded picture; and when the processing block is to be coded in inter mode or bi-prediction mode, the video encoder (603) may use an inter prediction or bi-prediction technique, respectively, to encode the processing block into the coded picture. In certain video coding technologies, merge mode can be an inter picture prediction submode where the motion vector is derived from one or more motion vector predictors without the benefit of a coded motion vector component outside the predictors. In certain other video coding technologies, a motion vector component applicable to the subject block may be present. In an example, the video encoder (603) includes other components, such as a mode decision module (not shown) to determine the mode of the processing blocks.

In the FIG. 6 example, the video encoder (603) includes the inter encoder (630), an intra encoder (622), a residue calculator (623), a switch (626), a residue encoder (624), a general controller (621), and an entropy encoder (625) coupled together as shown in FIG. 6.

The inter encoder (630) is configured to receive the samples of the current block (e.g., a processing block), compare the block to one or more reference blocks in reference pictures (e.g., blocks in previous pictures and later pictures), generate inter prediction information (e.g., description of redundant information according to inter encoding technique, motion vectors, merge mode information), and calculate inter prediction results (e.g., predicted block) based on the inter prediction information using any suitable technique. In some examples, the reference pictures are decoded reference pictures that are decoded based on the encoded video information.

The intra encoder (622) is configured to receive the samples of the current block (e.g., a processing block), in some cases compare the block to blocks already coded in the same picture, generate quantized coefficients after transform, and in some cases also intra prediction information (e.g., an intra prediction direction information according to one or more intra encoding techniques). In an example, the intra encoder (622) also calculates intra prediction results (e.g., predicted block) based on the intra prediction information and reference blocks in the same picture.

The general controller (621) is configured to determine general control data and control other components of the video encoder (603) based on the general control data. In an example, the general controller (621) determines the mode of the block, and provides a control signal to the switch (626) based on the mode. For example, when the mode is the intra mode, the general controller (621) controls the switch (626) to select the intra mode result for use by the residue calculator (623), and controls the entropy encoder (625) to select the intra prediction information and include the intra prediction information in the bitstream; and when the mode is the inter mode, the general controller (621) controls the switch (626) to select the inter prediction result for use by the residue calculator (623), and controls the entropy encoder (625) to select the inter prediction information and include the inter prediction information in the bitstream.

The residue calculator (623) is configured to calculate a difference (residue data) between the received block and prediction results selected from the intra encoder (622) or the inter encoder (630). The residue encoder (624) is configured to operate based on the residue data to encode the residue data to generate the transform coefficients. In an example, the residue encoder (624) is configured to convert the residue data from a spatial domain to a frequency domain, and generate the transform coefficients. The transform coefficients are then subject to quantization processing to obtain quantized transform coefficients. In various embodiments, the video encoder (603) also includes a residue decoder (628). The residue decoder (628) is configured to perform inverse-transform, and generate the decoded residue data. The decoded residue data can be suitably used by the intra encoder (622) and the inter encoder (630). For example, the inter encoder (630) can generate decoded blocks based on the decoded residue data and inter prediction information, and the intra encoder (622) can generate decoded blocks based on the decoded residue data and the intra prediction information. The decoded blocks are suitably processed to generate decoded pictures and the decoded pictures can be buffered in a memory circuit (not shown) and used as reference pictures in some examples.

The entropy encoder (625) is configured to format the bitstream to include the encoded block. The entropy encoder (625) is configured to include various information according to a suitable standard, such as the HEVC standard. In an example, the entropy encoder (625) is configured to include the general control data, the selected prediction information (e.g., intra prediction information or inter prediction information), the residue information, and other suitable information in the bitstream. Note that, according to the disclosed subject matter, when coding a block in the merge submode of either inter mode or bi-prediction mode, there is no residue information.

FIG. 7 shows a diagram of a video decoder (710) according to another embodiment of the disclosure. The video decoder (710) is configured to receive coded pictures that are part of a coded video sequence, and decode the coded pictures to generate reconstructed pictures. In an example, the video decoder (710) is used in the place of the video decoder (310) in the FIG. 3 example.

In the FIG. 7 example, the video decoder (710) includes an entropy decoder (771), an inter decoder (780), a residue decoder (773), a reconstruction module (774), and an intra decoder (772) coupled together as shown in FIG. 7.

The entropy decoder (771) can be configured to reconstruct, from the coded picture, certain symbols that represent the syntax elements of which the coded picture is made up. Such symbols can include, for example, the mode in which a block is coded (such as, for example, intra mode, inter mode, bi-predicted mode, the latter two in merge submode or another submode), prediction information (such as, for example, intra prediction information or inter prediction information) that can identify certain sample or metadata that is used for prediction by the intra decoder (772) or the inter decoder (780), respectively, residual information in the form of, for example, quantized transform coefficients, and the like. In an example, when the prediction mode is inter or bi-predicted mode, the inter prediction information is provided to the inter decoder (780); and when the prediction type is the intra prediction type, the intra prediction information is provided to the intra decoder (772). The residual information can be subject to inverse quantization and is provided to the residue decoder (773).

The inter decoder (780) is configured to receive the inter prediction information, and generate inter prediction results based on the inter prediction information.

The intra decoder (772) is configured to receive the intra prediction information, and generate prediction results based on the intra prediction information.

The residue decoder (773) is configured to perform inverse quantization to extract de-quantized transform coefficients, and process the de-quantized transform coefficients to convert the residual from the frequency domain to the spatial domain. The residue decoder (773) may also require certain control information (to include the Quantizer Parameter (QP)), and that information may be provided by the entropy decoder (771) (data path not depicted as this may be low volume control information only).

The reconstruction module (774) is configured to combine, in the spatial domain, the residual as output by the residue decoder (773) and the prediction results (as output by the inter or intra prediction modules as the case may be) to form a reconstructed block, that may be part of the reconstructed picture, which in turn may be part of the reconstructed video. It is noted that other suitable operations, such as a deblocking operation and the like, can be performed to improve the visual quality.

It is noted that the video encoders (303), (503), and (603), and the video decoders (310), (410), and (710) can be implemented using any suitable technique. In an embodiment, the video encoders (303), (503), and (603), and the video decoders (310), (410), and (710) can be implemented using one or more integrated circuits. In another embodiment, the video encoders (303), (503), and (503), and the video decoders (310), (410), and (710) can be implemented using one or more processors that execute software instructions.

Aspects of the disclosure provide techniques for merge/skip mode signaling. Various merge/skip modes are designed for inter-picture prediction coding to improve video coding for different video attributes. A skip mode generally operates in the same manner as a corresponding merge mode. But in the skip mode, no residual data is added to the predicted block, and in the merge mode, residual data is added to the predicted block. It is noted that while merge modes are used to illustrate signaling techniques, the signaling techniques can be suitably used for skip mode signaling.

In some examples, the merge modes can include a regular merge mode, a merge with motion vector difference (MMVD) mode, a sub-block based merge mode, a combined intra inter prediction (CIIP) mode, a triangle partition mode and the like. For example, at the encoder side, the encoder selects a specific merge mode from the merge modes to encode a block, and at the decoder side, the decoder reconstructs samples of the block using the specific merge mode. In some related examples, the specific merge mode is informed from the encoder side to the decoder side by signaling, and redundancy exists in the signaling of the various merge modes. The techniques provided in the present disclosure remove the signaling redundancy for the various merge modes, and improve coding efficiency.

In some examples, flags are used to signal different merge/skip modes. In some embodiments, a tree structure is used by encoder and decoder to make the merge mode decision. Based on the tree structure, flags are checked in a pre-defined order to determine the suitable merge mode to encode/decode a block. Table 1 shows a signaling method example for five types of merge modes using merge mode flags. In the Table 1 example, four merge mode flags, such as a regular flag, an MMVD flag, a sub-block flag, and a CIIP flag are used for signaling different types of merge modes.

TABLE 1 Flags for Signaling Different Types of Merge Modes Signaled Modes Regular MMVD Sub-block CIIP (Merge) Flag Flag Flag Flag Regular Merge 1 — — — MMVD 0 1 — — Sub-block based Merge 0 0 1 — CIIP 0 0 0 1 Triangle Partition 0 0 0 0

In an example, a block is encoded/decoded using a merge mode. According to Table 1, when the regular flag for the block is true (e.g., binary 1), the regular merge mode is used to encode/decode the block, no matter values of the other merge mode flags. When the regular flag for the block is false (e.g., binary 0) and the MMVD flag is true, the MMVD mode is used to encode/decode the block. When the regular flag and the MMVD flag are false and the sub-block flag is true, the sub-block based merge mode is used to encode/decode the block. When the regular flag, the MMVD flag and the sub-block flag are false and the CIIP flag is true, the CIIP mode is used to encode/decode the block. When the regular flag, the MMVD flag, the sub-block flag and the CIIP flag are false, the triangle partition mode is used to encode/decode the block.

Table 2 shows a signaling method for four types of skip modes. In the Table 2 example, three flags, such as a regular flag, an MMVD flag and a sub-block flag, are used for signaling different skip modes. It is noted that, in some examples, the same flag can be used to signal a merge mode or a skip mode that operates similar to the merge mode.

TABLE 2 Flags for Signaling Different Types of Skip Modes Signaled Modes Regular MMVD Sub-block (Skip) Flag Flag Flag Regular 1 — — MMVD 0 1 — Sub-block based 0 0 1 Triangle Partition 0 0 0

In an example, a block is encoded/decoded using a skip mode. According to Table 2, when the regular flag for the block is true (e.g., binary 1), the regular skip mode is used to encode/decode the block, no matter values of the other skip modes flags. When the regular flag for the block is false (e.g., binary 0) and the MMVD flag is true, the MMVD mode (skip) is used to encode/decode the block. When the regular flag and the MMVD flag are false and the sub-block flag is true, the sub-block based skip mode is used to encode/decode the block. When the regular flag, the MMVD flag and the sub-block flag are false, the triangle partition mode (skip) is used to encode/decode the block.

It is noted that while some descriptions in the present disclosure use merge modes as examples, the descriptions are not limited to the merge modes and can be suitably modified for skip modes.

According to some aspects of the disclosure, the merge mode decision depends on high level information (higher than the block level) and the information of the block. The high level information includes information in sequence parameter set (SPS), picture parameter set (PPS), slice header, tile group information, tile information, and the like. The information of the block includes size information of the block, such as width, height and area of the block. Table 3 shows a syntax table for merge modes.

TABLE 3 Syntax Table for Merge Modes merge_data( x0, y0, cbWidth, cbHeight ) { if ( CuPredMode[ x0 ][ y0 ] = = MODE_IBC ) { if( MaxNumMergeCand > 1 ) merge_idx[ x0 ][ y0 ] } else { regular_merge_flag[ x0 ][ y0 ] if ( regular_merge_flag[ x0 ][ y0 ] = = 1 ){ if( MaxNumMergeCand > 1 ) merge_idx[ x0 ][ y0 ] } else { if( sps_mmvd_enabled_flag && cbWidth × cbHeight != 32 ) mmvd_flag[ x0 ][ y0 ] if( mmvd_flag[ x0 ][ y0 ] = = 1 ) { if( MaxNumMergeCand > 1 ) mmvd_merge_flag[ x0 ][ y0 ] mmvd_distance_idx[ x0 ][ y0 ] mmvd_direction_idx[ x0 ][ y0 ] } else { if( MaxNumSubblockMergeCand > 0 && cbWidth >= 8 && cbHeight >= 8 ) merge_subblock_flag[ x0 ][ y0 ] if( merge_subblock_flag[ x0 ][ y0 ] = = 1 ) { if( MaxNumSubblockMergeCand > 1 ) merge_subblock_idx[ x0 ][ y0 ] } else { if( sps_ciip_enabled flag && cu_skip_flag[ x0 ][ y0 ] = = 0 && ( cbWidth * cbHeight ) >= 64 && cbWidth < 128 && cbHeight < 128 ) { ciip_flag[ x0 ][ y0 ] if( ciip_flag[ x0 ][ y0 ] && MaxNumMergeCand > 1 ) merge_idx[ x0 ][ y0 ] } if( MergeTriangleFlag[ x0 ][ y0 ] ) { merge_triangle_split_dir[ x0 ][ y0 ] merge_triangle_idx0[ x0 ][ y0 ] merge_triangle_idx1] x0 ][ y0 ] } } } } } }

In the Table 3 example, a tree structure is formed in the syntax to decide the suitable merge mode (signal a flag at the encoder side or parse a flag at the decoder side) to use on a block (e.g., top left corner is (x0, y0), block width is cbWidth, block height is cbHeight). The tree structure checks merge modes in an order, such as in an order of regular merge mode, MMV mode, sub-block based merge mode, CIIP mode and triangle partition mode. For a mode, an allowable condition for the mode is checked first, and when the allowable condition is satisfied, the flag may be signaled (at the encoder side) or parsed (at the decoder side.

In the Table 3 example, when the prediction mode of the block (e.g., CuPredMode[x0][y0]) is not intra block copy mode (MODE IBC), the tree structure is used for signaling (or parsing) information from the coded video bitstream for the appropriate merge mode.

Specifically, in the Table 3 example, the regular flag (regular_merge_flag) for the regular merge mode is signaled. When the regular flag is true, merge index (merge_index) is signaled.

In some examples (e.g., VVC draft 5), the regular merge mode is allowed when a variable MaxNumMergeCand in the slice header is greater than 0, and the variable MaxNumMergeCand is used to signal the maximum number of merge candidates.

In an example, a variable allowRegularMerge is used to indicate whether the regular merge mode is allowed or not. For example, the variable allowRegularMerge can be defined as in (Eq. 1)

allowRegularMerge=MaxNumMergeCand>0  (Eq. 1)

Thus, when MaxNumMergeCand is greater than 0, allowRegularMerge is true; otherwise, allowRegularMerge is false for example.

Further, in the Table 3 example, when the regular flag is false, the MMVD mode is checked. The MMVD mode is enabled by a flag sps_mmvd_enabled_flag in SPS. In an example, MMVD mode is signaled when sps_mmvd_enabled_flag is true and a block size requirement is satisfied. In an example, cbWidth denotes the width of the coding block, cbHeight denotes the height of the coding block. Then, MMVD flag (mmvd_flag) is signaled when sps_mmvd_enabled_flag is true and cbWidth×cbHeight is not equal to 32. When the MMVD flag is true, other suitable information for the MMVD mode is signaled.

It is noted that when cbWidth×cbHeight is equal to 32, only regular merge mode and MMVD mode is allowed. In an example that cbWidth×cbHeight is equal to 32, when the regular flag is false, then the prediction mode is the MMVD mode, and the MMVD flag can be inferred to be true. In this example, MMVD flag is not need to be signaled from the encoder side to the decoder side. This example removes redundancy for the MMVD mode signaling.

In some examples, a variable allowMMVD is used to indicate whether MMVD mode is allowed or not. The variable allowMMVD can be defined as in (Eq. 2):

allowMMVD=sps_mmvd_enabled_flag  (Eq. 2)

Further, in the Table 3 example, when the MMVD flag is false, the sub-block based merge mode is checked. The sub-block based merge mode is allowed when a variable MaxNumSubblockMergeCand which is based on information signaled in slice header is greater than 0 and the cbWidth and cbHeight are respectively greater than or equal to 8. In an example, when the sub-block based merge mode is allowed, the sub-block flag (merge_subblock_flag) is signaled. When the sub-block flag is true, other suitable information for the sub-block based merge mode can be signaled.

In an example, a variable allowSubMerge is used to indicate whether the sub-block based merge mode is allowed or not. The variable allowSubMerge can be defined as in (Eq. 3):

allowSubMerge=MaxNumSubblockMergeCand>0&& cbWidth>=8&& cbHeight>=8  (Eq. 3)

Further, in the Table 3 example, when the sub-block flag is false, the CIIP mode is checked. The CIIP mode is allowed when sps_ciip_enabled_flag is true, the current block is not skip mode, cbWidth×cbHeight is no smaller than 64, cbWidth is smaller than 128, and cbHeight is smaller than 128. In an example, when the CIIP mode is allowed, the CIIP flag is signaled. When the CIIP flag is true, other suitable information for the CIIP mode can be signaled.

In an example, a variable allowCIIP is used to indicate whether the CIIP mode is allowed or not. The variable allowCIIP is defined as in (Eq. 4):

allowCIIP=sps_ciip_enabled_flag&&!cu_skip_flag&& cbWidth×cbHeight>=64 && cbWidth<128 && cbHeight<128  (Eq. 4)

In some examples, the triangle merge mode can be inferred instead of signaling. When, the regular flag, the MMVD flag, the sub-block flag, the CIIP flag are all false, then the triangle merge mode may be enabled. To allow the triangle merge mode, sps_triangle_enabled_flag needs to be true, the current slice has to be B slice, MaxNumTriangleMergeCand which is based on information signaled in slice header is greater than or equal to 2, and cbWidth×cbHeight is greater than or equal to 64. In an example, a variable allowTriangle is used to indicate whether triangle merge mode is allowed. The variable allowTriangle can be defined as in (Eq. 5):

allowTriangle=sps_triangle_enabled_flag && slice_type==B&& MaxNumTriangleMergeCand>=2&&cbWidth×cbHeight>=64  (Eq. 5)

In some related examples, the regular flag is always signaled. However, this is not necessary since under some conditions, the encoder and decoder can only choose regular merge mode.

According to some aspects of the disclosure, at encoder side, before signaling a merge mode flag for a merge mode, certain condition is checked to determine whether the merge mode flag can be inferred. When the condition satisfies a requirement for inferring the merge mode flag, then the encoder does not need to signal the merge mode flag. At the decoder side, the decoder may check the condition to determine whether the merge mode flag can be inferred. When the condition satisfies the requirement for inferring the merge mode flag, the decoder does not parse the coded video bitstream for the merge mode flag, and can infer the merge mode flag. Thus, signaling redundancy can be removed.

In some embodiments, when a merge mode flag has only one possible value under a predefined condition, the merge mode flag is inferred instead of explicit signaling. The merge modes that can be inferred may include but not limited to the regular merge mode, the MMVD mode, the sub-block based merge mode, the CIIP mode, and the triangle mode.

FIG. 8 shows a flow chart of an algorithm for an encoder (decoder) to signal (parse) merge mode flags. In the FIG. 8 example, under certain conditions, some merge mode flags are inferred instead of being signaled (parsed). Thus, the signaling cost is saved and redundancy can be removed. In an example, the algorithm in FIG. 8 is performed by processing circuitry of an encoder. In another example, the algorithm in FIG. 8 is performed by processing circuitry of a decoder.

In the FIG. 8 example, the coding order of the tree structure starts with regular merge mode and follows by MMVD mode, sub-block based merge mode, CIIP mode and triangle partition mode subsequently. It is noted that, when the tree structure changes, the corresponding conditions can be changed accordingly.

It is also noted that (Eq. 3)-(Eq. 5) are merely examples for defining variables for certain conditions. The conditions can be defined in other suitable ways.

For example, (Eq. 3) defines the variable allowSubMerge as a combination of several sub-conditions. The variable allowSubMerge can be indicated by sub-conditions. In an embodiment, the variable allowSubMerge is equal to MaxNumSubMergeCand>0. For example, when the variable MaxNumSubMergeCand is greater than zero, the variable allowSubMerge is true (e.g., binary 1); and when the variable MaxNumSubMergeCand is equal to zero, the variable allowSubMerge is false (e.g., binary 0). In another embodiment, the variable allowSubMerge is equal to (cbWidth>=8 and cbHeight>=8). For example, when both of the width and the height of the coding block is larger than 8, the variable allowSubMerge is true; otherwise the variable allowSubMerge is false.

In another example, (Eq. 4) defines the variable allowCIIP as a combination of several sub-conditions. The variable allowCIIP can be defined by sub-conditions. In an embodiment, the variable allowSubMerge is equal to sps_ciip_enabled_flag. In another embodiment, the variable allowSubMerge is equal to !cu_skip_flag. For example, when the flag cu_skip_flag is true, the variable allowSubMerge is false; and when the flag cu_skip_flag is false, the variable allowSubMerge is true. In another embodiment, the variable allowSubMerge is equal to (cbWidth×cbHeight>=64). For example, when the area of the block is equal to or larger than 64, the variable allowSubMerge is true; otherwise, the variable allowSubMerge is false. In another embodiment, allowSubMerge is equal to (cbWidth<128 and cbHeight<128). For example, when both the width and the height of the coding block are smaller than 128, the variable allowSubMerge is true; otherwise, the variable allowSubMerge is false.

In another example, (Eq. 5) defines the allowTriangle as a combination of several sub-conditions. The variable allowTriangle can be defined by sub conditions. In an embodiment, variable allowTriangle is equal to sps_triangle_enbaled_flag. In another embodiment, the variable allowTriangle is set based on slice_type. When the slice_type is B (bi-direction prediction), the variable allowTriangle is true; and when the slice_type is not B, the variable allowTriangle is false. In another embodiment, the variable allowTriangle is equal to (MaxTriangleMergeCand>=2). For example, when the variable MaxTriangleMergeCand is equal to or larger than 2, the variable allowTriangle is true; otherwise, the variable allowTriangle is false. In another embodiment, the variable allowTriangle is equal to (cbWidth×cbHeight>=64). For example, when the area of the coding block is equal to or larger than 64, the variable allowTriangle is true; otherwise, the variable allowTriangle is false.

Referring back to FIG. 8, the algorithm starts at (S801) and proceeds to (S810).

At (S810), a first condition (allowRegularMerge &&(allowMMVD∥allowSubMerge∥allowCIIP∥allowTriangle)) is checked. When the first condition is true, the algorithm proceeds to (S812); and when the first condition is false, the algorithm proceeds to the (S815).

At (S812), the regular flag is signaled (parsed by the decoder) from the encoder side.

At (S815), the regular flag is not signaled but inferred. In an example, when allowRegularMerge is false, the regular flag is inferred to be false. In another example, when (allowMMVD∥allowSubMerge∥allowCIIP∥allowTriangle) is false, the regular flag is inferred to be true.

In some examples, the variables allowRegularMerge, allowMMVD, allowSubMerge, allowCIIP, allowTriangle are defined as in (Eq. 1) (Eq. 2) (Eq. 3) (Eq. 4) and (Eq. 5).

It is noted that the variables allowSubMerge, allowCIIP, and allowTriangle can be defined in other suitable manner. In some examples, some of the conditions of the merge modes are overlapped, for example, when cbWidth×cbHeight is smaller than 64 (for example, block width times block height is equal to 32), sub-block based merge mode, CIIP, and triangle partition mode are all disabled. When sps_mmvd_enabled_flag is false, and the cbWidth×cbHeight is smaller than 64, the MMVD mode, sub-block based merge mode, CIIP mode, and the triangle partition mode are all disabled. In such case, only regular merge mode is enabled.

At (S820), the regular flag is checked. When the regular flag is true, the algorithm proceeds to (S825); otherwise, the algorithm proceeds to (S830).

At (S825), the regular flag is true, the algorithm returns the regular merge mode, and stop. The block is then encoded (decoded) based on the regular merge mode.

At (S830), a second condition (allowMMVD && (allowSubMerge∥allowCIIP∥allowTriangle)) is checked. When the second condition is true, the algorithm proceeds to (S832); and when the second condition is false, the algorithm proceeds to (S835).

At (S832), the MMVD flag is signaled (parsed by the decoder) from the encoder side.

At (S835), the MMVD flag is not signaled but inferred. In an example, when allowMMVD is false, the MMVD flag is inferred to be false. In another example, when (allowSubMerge∥allowCIIP∥allowTriangle) is false, the MMVD flag is inferred to be true. In some examples, the variables allowMMVD, allowSubMerge, allowCIIP, allowTriangle are defined as in (Eq. 2) (Eq. 3) (Eq. 4) and (Eq. 5). It is noted that the variables allowMMVD, allowSubMerge, allowCIIP, and allowTriangle can be defined in other suitable manner.

At (S840), the MMVD flag is checked. When the MMVD flag is true, the algorithm proceeds to (S845); otherwise, the algorithm proceeds to (S850).

At (S845), the MMVD flag is true, the algorithm returns the MMVD mode, and stop. The block is then encoded (decoded) based on the MMVD mode.

At (S850), a third condition (allowSubMerge &&(allowCIIP∥allowTriangle)) is checked. When the third condition is true, the algorithm proceeds to (S852); when the third condition is false, the algorithm proceeds to (S855).

At (S852), the sub-block flag is signaled (parsed by the decoder) from the encoder side.

At (S855), the sub-block flag is not signaled but inferred. In an example, when allowSubMerge is false, the sub-block flag is inferred to be false. In another example, when (allowCIIP∥allowTriangle) is false, the sub-block flag is inferred to be true. In some examples, the variables allowSubMerge, allowCIIP, allowTriangle are defined as in (Eq. 3) (Eq. 4) and (Eq. 5). It is noted that the variables allowSubMerge, allowCIIP, and allowTriangle can be defined in other suitable manner.

At (S860), the sub-block flag is checked. When the sub-block flag is true, the algorithm proceeds to (S865); otherwise, the algorithm proceeds to (S870).

At (S865), the sub-block flag is true, the algorithm returns the sub-block based merge mode, and stop. The block is then encoded (decoded) based on the sub-block based merge mode.

At (S870), a fourth condition (allowCIIP && allowTriangle) is checked. When the fourth condition is true, the algorithm proceeds to (S872); when the fourth condition is false, the algorithm proceeds to (S875).

At (S872), the CIIP flag is signaled (parsed by the decoder) from the encoder side.

At (S875), the CIIP flag is not signaled but inferred. In an example, when allowSubMerge is false, the CIIP flag is inferred to be false. In another example, when allowTriangle is false, the CIIP flag is inferred to be true. In some examples, the variable allowCIIP and allowTriangle are defined as in (Eq. 4) and (Eq. 5). It is noted that the variables allowCIIP, and allowTriangle can be defined in other suitable manner.

At (S880), the CIIP flag is checked. When the CIIP flag is true, the algorithm proceeds to (S882); otherwise, the algorithm proceeds to (S885).

At (S882), the CIIP flag is true, the algorithm returns the CIIP mode, and stop. The block is then encoded (decoded) based on the CIIP mode.

At (S885), the algorithm returns the triangle partition mode and stop. The block is then encoded(decoded) based on the triangle partition mode.

It is noted that, in some examples, for inter prediction, the allowed cbWidth and cbHeight are already defined for each mode. However, in some examples, the allowed cbWidth and cbHeight may change, then the variables and conditions can be suitably changed.

In some embodiments, N is defined as the minimum allowed width, M is defined as the minimum allowed height, K is defined as the minimum area, H is defined as the upper limit for width, L is defined as upper limit for height, and O is defined as upper limit for area. M, N, K, H, L, O are non-negative integers. In an example, then the variables allowSubMerge, allowCIIP and allowTriangle can be defined as in (Eq. 6)-(Eq. 8)

allowSubMerge=MaxNumSubblockMergeCand>0&&cbWidth>=N&&cbHeight>=M   (Eq. 6)

allowCIIP=sps_ciip_enabled_flag&&!cu_skip_flag&&cbWidth×cbHeight>=K&&cbWidth<H&& cbHeight<L  (Eq. 7)

allowTriangle=sps_triangle_enabled_flag&&slice_type is equal to B&&MaxNumTriangleMergeCand>=2&&cbWidth×cbHeight>=0  (Eq. 8)

According to another aspect of the disclosure, redundancy of the merge mode signaling can be removed by context. In some embodiments, more contexts for the regular flag, MMVD flag, sub-block flag, CIIP flag are added. When selecting a context, the context can be based on the block size, or sps enabling flags or slice type. Partial of or all the above signaling conditions can be used to select the context.

In an embodiment, the regular flag can be based on the block width times block height, for example, when cbWidth×cbHeight<size threshold, one context is used. Otherwise, another context is used.

According to another aspect of the disclosure, conditional checks for signaling MMVD flag can be removed. In some examples, MMVD flag is signaled without checking the block size to speed up the decoding process. Table 4 shows the syntax example for signaling MMVD flag.

TABLE 4 Syntax for signaling MMVD flag merge_data( x0, y0, cbWidth, cbHeight ) { if ( CuPredMode[ x0 ][ y0 ] = = MODE_IBC ) { if( MaxNumMergeCand > 1 ) merge_idx[ x0 ][ y0 ] } else { regular_merge_flag[ x0 ][ y0 ] if ( regular_merge_flag[ x0 ][ y0 ] = = 1 ){ if( MaxNumMergeCand > 1 ) merge_idx[ x0 ][ y0 ] } else { if( sps_mmvd_enabled_flag ) mmvd_flag[ x0 ][ y0 ] ... } } } }

Comparing Table 4 with Table 3, the MMVD flag is signaled without checking the block size (e.g., block width, block height) in Table 4.

In some embodiments, to avoid broken bitstreams, a conformance constraint can be added. In an example, a conformance constraint constrains the general merge flag and the skip flag. For example, when regular flag is false, MMVD flag is false, sub-bloc flag is false, CIIP flag is false, and triangle flag is false, then the general merge flag and skip flag must be false according to the conformance constraint.

In another example, another conformance constraint is added. When the value of (cbWidth×cbHeight) is equal to 32 and the regular flag is false, then the MMVD flag is signaled as true according to the conformance constraint.

FIG. 9 shows a flow chart outlining a process (900) according to an embodiment of the disclosure. The process (900) can be used to determine a prediction mode for a block, so to generate a prediction block for the block under reconstruction based on the prediction mode. In various embodiments, the process (900) are executed by processing circuitry, such as the processing circuitry in the terminal devices (210), (220), (230) and (240), the processing circuitry that performs functions of the video encoder (303), the processing circuitry that performs functions of the video decoder (310), the processing circuitry that performs functions of the video decoder (410), the processing circuitry that performs functions of the video encoder (503), and the like. In some embodiments, the process (900) is implemented in software instructions, thus when the processing circuitry executes the software instructions, the processing circuitry performs the process (900). The process starts at (S901) and proceeds to (S910).

At (S910), an inferable condition for a flag associated with a specific prediction mode for a current block is checked before parsing the flag of the specific prediction mode for the current block from a coded video bitstream. The specific prediction mode is one of a plurality of inter picture prediction modes. In an example, the specific prediction mode is one of merge modes. In another example, the specific prediction mode is one of skip modes. In some embodiments, the plurality inter picture prediction modes form a tree structure for making a decision of a prediction mode for the current block. When the inferable condition is indicative of inferable, the process proceeds to (S920); otherwise, the process proceeds to (S930).

At (S920), the flag associated with the specific prediction mode is inferred without parsing the flag from the coded video bitstream. In an example, when the flag can be inferred, the flag is not signaled in the coded video bitstream to reduce signal redundancy.

At (S930), the flag associated with the specific prediction mode is parsed from the coded video bitstream.

At (S940), the flag is checked to determine whether the flag is indicative of an application of the specific prediction mode on the current block. When the flag is indicative of an application of the specific prediction mode, the process proceeds to (S950); otherwise, the process proceeds to (S960).

At (S950), samples of the current block are reconstructed according to the specific prediction mode. The process proceeds to S999 and terminates.

At (S960), the process continues to decode a next flag in the tree structure.

The techniques described above, can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media. For example, FIG. 10 shows a computer system (1000) suitable for implementing certain embodiments of the disclosed subject matter.

The computer software can be coded using any suitable machine code or computer language, that may be subject to assembly, compilation, linking, or like mechanisms to create code comprising instructions that can be executed directly, or through interpretation, micro-code execution, and the like, by one or more computer central processing units (CPUs), Graphics Processing Units (GPUs), and the like.

The instructions can be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smartphones, gaming devices, internet of things devices, and the like.

The components shown in FIG. 10 for computer system (1000) are exemplary in nature and are not intended to suggest any limitation as to the scope of use or functionality of the computer software implementing embodiments of the present disclosure. Neither should the configuration of components be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary embodiment of a computer system (1000).

Computer system (1000) may include certain human interface input devices. Such a human interface input device may be responsive to input by one or more human users through, for example, tactile input (such as: keystrokes, swipes, data glove movements), audio input (such as: voice, clapping), visual input (such as: gestures), olfactory input (not depicted). The human interface devices can also be used to capture certain media not necessarily directly related to conscious input by a human, such as audio (such as: speech, music, ambient sound), images (such as: scanned images, photographic images obtain from a still image camera), video (such as two-dimensional video, three-dimensional video including stereoscopic video).

Input human interface devices may include one or more of (only one of each depicted): keyboard (1001), mouse (1002), trackpad (1003), touch screen (1010), data-glove (not shown), joystick (1005), microphone (1006), scanner (1007), camera (1008).

Computer system (1000) may also include certain human interface output devices. Such human interface output devices may be stimulating the senses of one or more human users through, for example, tactile output, sound, light, and smell/taste. Such human interface output devices may include tactile output devices (for example tactile feedback by the touch-screen (1010), data-glove (not shown), or joystick (1005), but there can also be tactile feedback devices that do not serve as input devices), audio output devices (such as: speakers (1009), headphones (not depicted)), visual output devices (such as screens (1010) to include CRT screens, LCD screens, plasma screens, OLED screens, each with or without touch-screen input capability, each with or without tactile feedback capability—some of which may be capable to output two dimensional visual output or more than three dimensional output through means such as stereographic output; virtual-reality glasses (not depicted), holographic displays and smoke tanks (not depicted)), and printers (not depicted).

Computer system (1000) can also include human accessible storage devices and their associated media such as optical media including CD/DVD ROM/RW (1020) with CD/DVD or the like media (1021), thumb-drive (1022), removable hard drive or solid state drive (1023), legacy magnetic media such as tape and floppy disc (not depicted), specialized ROM/ASIC/PLD based devices such as security dongles (not depicted), and the like.

Those skilled in the art should also understand that term “computer readable media” as used in connection with the presently disclosed subject matter does not encompass transmission media, carrier waves, or other transitory signals.

Computer system (1000) can also include an interface to one or more communication networks. Networks can for example be wireless, wireline, optical. Networks can further be local, wide-area, metropolitan, vehicular and industrial, real-time, delay-tolerant, and so on. Examples of networks include local area networks such as Ethernet, wireless LANs, cellular networks to include GSM, 3G, 4G, 5G, LTE and the like, TV wireline or wireless wide area digital networks to include cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial to include CANBus, and so forth. Certain networks commonly require external network interface adapters that attached to certain general purpose data ports or peripheral buses (1049) (such as, for example USB ports of the computer system (1000)); others are commonly integrated into the core of the computer system (1000) by attachment to a system bus as described below (for example Ethernet interface into a PC computer system or cellular network interface into a smartphone computer system). Using any of these networks, computer system (1000) can communicate with other entities. Such communication can be uni-directional, receive only (for example, broadcast TV), uni-directional send-only (for example CANbus to certain CANbus devices), or bi-directional, for example to other computer systems using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.

Aforementioned human interface devices, human-accessible storage devices, and network interfaces can be attached to a core (1040) of the computer system (1000).

The core (1040) can include one or more Central Processing Units (CPU) (1041), Graphics Processing Units (GPU) (1042), specialized programmable processing units in the form of Field Programmable Gate Areas (FPGA) (1043), hardware accelerators for certain tasks (1044), and so forth. These devices, along with Read-only memory (ROM) (1045), Random-access memory (1046), internal mass storage such as internal non-user accessible hard drives, SSDs, and the like (1047), may be connected through a system bus (1048). In some computer systems, the system bus (1048) can be accessible in the form of one or more physical plugs to enable extensions by additional CPUs, GPU, and the like. The peripheral devices can be attached either directly to the core's system bus (1048), or through a peripheral bus (1049). Architectures for a peripheral bus include PCI, USB, and the like.

CPUs (1041), GPUs (1042), FPGAs (1043), and accelerators (1044) can execute certain instructions that, in combination, can make up the aforementioned computer code. That computer code can be stored in ROM (1045) or RAM (1046). Transitional data can be also be stored in RAM (1046), whereas permanent data can be stored for example, in the internal mass storage (1047). Fast storage and retrieve to any of the memory devices can be enabled through the use of cache memory, that can be closely associated with one or more CPU (1041), GPU (1042), mass storage (1047), ROM (1045), RAM (1046), and the like.

The computer readable media can have computer code thereon for performing various computer-implemented operations. The media and computer code can be those specially designed and constructed for the purposes of the present disclosure, or they can be of the kind well known and available to those having skill in the computer software arts.

As an example and not by way of limitation, the computer system having architecture (1000), and specifically the core (1040) can provide functionality as a result of processor(s) (including CPUs, GPUs, FPGA, accelerators, and the like) executing software embodied in one or more tangible, computer-readable media. Such computer-readable media can be media associated with user-accessible mass storage as introduced above, as well as certain storage of the core (1040) that are of non-transitory nature, such as core-internal mass storage (1047) or ROM (1045). The software implementing various embodiments of the present disclosure can be stored in such devices and executed by core (1040). A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the core (1040) and specifically the processors therein (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM (1046) and modifying such data structures according to the processes defined by the software. In addition or as an alternative, the computer system can provide functionality as a result of logic hardwired or otherwise embodied in a circuit (for example: accelerator (1044)), which can operate in place of or together with software to execute particular processes or particular parts of particular processes described herein. Reference to software can encompass logic, and vice versa, where appropriate. Reference to a computer-readable media can encompass a circuit (such as an integrated circuit (IC)) storing software for execution, a circuit embodying logic for execution, or both, where appropriate. The present disclosure encompasses any suitable combination of hardware and software.

Appendix A: Acronyms

JEM: joint exploration model VVC: versatile video coding BMS: benchmark set

MV: Motion Vector HEVC: High Efficiency Video Coding SEI: Supplementary Enhancement Information VUI: Video Usability Information GOPs: Groups of Pictures TUs: Transform Units, PUs: Prediction Units CTUs: Coding Tree Units CTBs: Coding Tree Blocks PBs: Prediction Blocks HRD: Hypothetical Reference Decoder SNR: Signal Noise Ratio CPUs: Central Processing Units GPUs: Graphics Processing Units CRT: Cathode Ray Tube LCD: Liquid-Crystal Display OLED: Organic Light-Emitting Diode CD: Compact Disc DVD: Digital Video Disc ROM: Read-Only Memory RAM: Random Access Memory ASIC: Application-Specific Integrated Circuit PLD: Programmable Logic Device LAN: Local Area Network

GSM: Global System for Mobile communications

LTE: Long-Term Evolution CANBus: Controller Area Network Bus USB: Universal Serial Bus PCI: Peripheral Component Interconnect FPGA: Field Programmable Gate Areas

SSD: solid-state drive

IC: Integrated Circuit CU: Coding Unit

While this disclosure has described several exemplary embodiments, there are alterations, permutations, and various substitute equivalents, which fall within the scope of the disclosure. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the disclosure and are thus within the spirit and scope thereof. 

1. (canceled)
 2. A method for video decoding in a decoder, comprising: checking, by a processor, an inferable condition for a flag of a specific prediction mode for a current block before parsing the flag of the specific prediction mode for the current block from a coded video bitstream, the specific prediction mode being one of a plurality of inter picture prediction modes, the inferable condition being based on at least whether the specific prediction mode is allowed, the allowability of the specific prediction mode being determined based on size information of a current block; inferring, by the processor, the flag without parsing the flag from the coded video bitstream when the inferable condition indicates that the flag is inferable; parsing, by the processor, the flag from the coded video bitstream when the inferable condition indicates uncertainty for inferring the flag; and reconstructing, by the processor, the current block according to the specific prediction mode when the flag is indicative of an application of the specific prediction mode on the current block.
 3. The method of claim 2, wherein the inferable condition is further based on whether other modes in the plurality of inter prediction modes are allowed.
 4. The method of claim 2, wherein the flag is one of a regular flag of a regular merge/skip mode, a merge with motion vector difference (MMVD) flag of a MMVD mode, a sub-block flag of a sub-block based merge/skip mode, a combined intra inter prediction (CIIP) flag of a CIIP mode, a triangle flag of a triangle partition mode.
 5. The method of claim 3, wherein the other modes are at a lower level than the specific prediction mode in a tree structure.
 6. The method of claim 3, wherein the inferable condition is a combination of the allowability of the specific prediction mode and the allowability of the other modes that are at a lower level than the specific prediction mode in a tree structure.
 7. The method of claim 2, wherein the inferable condition indicates that the flag is inferable when the specific prediction mode is not allowed.
 8. The method of claim 3, wherein the inferable condition indicates that the flag is inferable when none of the other modes are allowed.
 9. The method of claim 2, wherein whether the other modes in the plurality of inter prediction modes are allowed is determined based on at least one of a sequence parameter set (SPS), a picture parameter set (PPS), a slice header, tile information, and tile group information.
 10. An apparatus for video decoding, comprising: processing circuitry configured to: check an inferable condition for a flag of a specific prediction mode for a current block before parsing the flag of the specific prediction mode for the current block from a coded video bitstream, the specific prediction mode being one of a plurality of inter picture prediction modes, the inferable condition being based on at least whether the specific prediction mode is allowed, the allowability of the specific prediction mode being determined based on size information of a current block; infer the flag without parsing the flag from the coded video bitstream when the inferable condition indicates that the flag is inferable; parse the flag from the coded video bitstream when the inferable condition indicates uncertainty for inferring the flag; and reconstruct the current block according to the specific prediction mode when the flag is indicative of an application of the specific prediction mode on the current block.
 11. The apparatus of claim 10, wherein the inferable condition is further based on whether other modes in the plurality of inter prediction modes are allowed.
 12. The apparatus of claim 11, wherein the flag is one of a regular flag of a regular merge/skip mode, a merge with motion vector difference (MMVD) flag of a MMVD mode, a sub-block flag of a sub-block based merge/skip mode, a combined intra inter prediction (CIIP) flag of a CIIP mode, a triangle flag of a triangle partition mode.
 13. The apparatus of claim 11, wherein the other modes are at a lower level than the specific prediction mode in a tree structure.
 14. The apparatus of claim 11, wherein the inferable condition is a combination of the allowability of the specific prediction mode and the allowability of the other modes that are at a lower level than the specific prediction mode in a tree structure.
 15. The apparatus of claim 10, wherein the inferable condition indicates that the flag is inferable when the specific prediction mode is not allowed.
 16. The apparatus of claim 11, wherein the inferable condition indicates that the flag is inferable when none of the other modes are allowed.
 17. The apparatus of claim 11, wherein whether the other modes in the plurality of inter prediction modes are allowed is determined based on at least one of a sequence parameter set (SPS), a picture parameter set (PPS), a slice header, tile information, and tile group information.
 18. A non-transitory computer-readable medium storing instructions which when executed by a computer for video decoding cause the computer to perform: checking an inferable condition for a flag of a specific prediction mode for a current block before parsing the flag of the specific prediction mode for the current block from a coded video bitstream, the specific prediction mode being one of a plurality of inter picture prediction modes, the inferable condition being based on at least whether the specification prediction mode is allowed, the allowability of the specific prediction mode being determined based on size information of a current block; inferring the flag without parsing the flag from the coded video bitstream when the inferable condition indicates that the flag is inferable; parsing the flag from the coded video bitstream when the inferable condition indicates uncertainty for inferring the flag; and reconstructing the current block according to the specific prediction mode when the flag is indicative of an application of the specific prediction mode on the current block.
 19. The non-transitory computer readable medium according to claim 18, wherein the inferable condition is further based on whether other modes in the plurality of inter prediction modes are allowed.
 20. The non-transitory computer readable medium according to claim 18, wherein the flag is one of a regular flag of a regular merge/skip mode, a merge with motion vector difference (MMVD) flag of a MMVD mode, a sub-block flag of a sub-block based merge/skip mode, a combined intra inter prediction (CIIP) flag of a CIIP mode, a triangle flag of a triangle partition mode.
 21. The non-transitory computer readable medium according to claim 19, wherein the other modes are at a lower level than the specific prediction mode in a tree structure. 